-
Notifications
You must be signed in to change notification settings - Fork 107
Make Serializer and some of his methods public
#388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
As the original movers and drivers of the serializer feature getting merged at all @Michael-F-Bryan and @RumovZ, do you have any input relevant to making these bits public? |
|
Tangentially related, #374. |
|
Nope, wouldn't mind. |
|
Any news? |
zbraniecki
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
|
Are we ready to merge? @alerque |
|
Any news? |
1 similar comment
|
Any news? |
|
We're currently looking into building tooling around converting gettext PO files to FTL files and adding some utilities for renaming identifiers and keeping FTL files tidy for fish1. For this, we would need to be able to parse FTL files, modify the parsed data, and serialize it back so that we can update the FTL files. I just started looking into the available APIs from This PR is very small (it only adds a few Footnotes |
|
Since this was approved, I'm going to go ahead and land this. |
I use this methods to serialize text into Message/Term/etc in my Fluent Extractor.
It would be great to make them public